Automatic After Call Social Messaging Connection Platform

ABSTRACT

This disclosure provides methods, systems, services, and platforms for automatically prompting a user of a mobile device to follow an entity on a social media network after a triggering event. This disclosure enables Mobile Network Operators to generate more followers on social media, and, thereby, connect better with potential customers or fans. When a business, group, or other entity has an active social media campaign, a message comprising instructions to launch a browser on a mobile device and navigate to the entity&#39;s social media page is sent automatically after a triggering event occurs.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/156,723, filed May 4, 2015. The entire contents of thatapplication are incorporated herein by reference.

FIELD

This application relates to mobile devices and mobile networks.Specifically, this application relates to data pertaining to mobiledevices and mobile networks.

BACKGROUND

Companies and brands are always looking for new ways to connect withconsumers. With the advent of social media, businesses are now reachingout to new and existing customers through photo feeds like Instagram,interest boards like Pinterest, quick news and promotions vehicles likeTwitter, and informal events and communications sites such as Facebook.While brands may find it easy to set up social media profiles, theytypically find it difficult to connect directly with consumers.Consumers may already be using social media platforms like Facebook andTwitter, but may not think to connect to a business unless they aredirectly invited to do so at a relevant and convenient time. Companiesneed a quick, simple, and personalized way to reach their consumer baseto connect on social media platforms.

SUMMARY

One aspect of this disclosure provides a computer-implemented method forautomatically prompting a user to follow an entity on a social medianetwork on a mobile device after a triggering event. The methodcomprises: receiving, at a server, an indication that a triggering eventhas occurred; receiving, at the server, an indication that thetriggering event matches a triggering event stored in a databaseoperably connected to the server; receiving, at the server, acommunication comprising the Mobile Station International SubscriberDirectory Number of the mobile device; preparing a first social mediamessage comprising one or more first actionable response options; andsending the first social media message to the mobile device.

In some embodiments, the triggering event is selected from the groupconsisting of a phone call placed from the mobile device to a firstphone number, a phone call received at the mobile device from a secondphone number, navigation to a specific web address on the mobile device,and navigation away from a specific web address on the mobile device. Incertain embodiments, the triggering event is a phone call placed fromthe mobile device to a first phone number.

In some embodiments, the entity is selected from the group consisting ofa business, a university, and a political campaign.

In some embodiments, the social media network is selected from the groupconsisting of Facebook, Instragram, Twitter, Google+, LinkedIn, Renren,Snapchat, Tumblr, Pinterest, and YouTube. In some embodiments, thesocial media network is any social media network that allows followers.

In some embodiments of the method, the first social media message isselected from the group consisting of binary SMS, flash SMS, MMS,standard SMS, USSD notification, and email.

In some embodiments, the method further comprises: receiving, at theserver, a communication comprising the first actionable response optionselected on the mobile device; preparing a second social media messagecomprising executable instructions to launch a browser on the mobiledevice and to navigate the browser to a social media website address;and sending the second social media message to the mobile device. Insome embodiments, the method also comprises logging the first actionableresponse option selected by the user. In further embodiments, the methodcomprises determining whether social media messages sent to the mobiledevice have exceeded a preset amount. In still other embodiments of themethod, the communication further comprises the device type of themobile device and information regarding whether the mobile devicesupports browser launch from executable instructions contained within areceived message.

In some embodiments, the further comprises: preparing an SMS messagecomprising a browser launch link; and sending the SMS message to themobile device, wherein the SMS message is prepared and sent when theinformation indicates that the mobile device does not support browserlaunch from instructions contained within a received message.

Another aspect of this disclosure provides a computer-implemented methodfor automatically prompting a user to follow an entity on a social medianetwork after a triggering event on a mobile device. The methodcomprises: receiving, at the processor in the mobile phone, anindication that a triggering event has occurred; receiving at the mobiledevice a first social media message comprising one or more firstactionable response options; and displaying on the screen of the mobiledevice the first social media message.

In some embodiments of the method the triggering event is selected fromthe group consisting of a phone call placed from the mobile device to afirst phone number, a phone call received at the mobile device from asecond phone number, navigation to a specific web address on the mobiledevice, and navigation away from a specific web address on the mobiledevice. In certain embodiments, the triggering event is a phone callplaced from the mobile device to a first phone number.

In some embodiments of the method, the first social media message isselected from the group consisting of binary SMS, flash SMS, MMS,standard SMS, USSD notification, and email.

In some embodiments of the method, the entity is selected from the groupconsisting of a business, a university, and a political campaign.

In some embodiments of the method, the social media network is selectedfrom the group consisting of Facebook, Instragram, Twitter, Google+,LinkedIn, Renren, Snapchat, Tumblr, Pinterest, and YouTube.

In some embodiments, the method further comprises playing an alert toneon the mobile device when the first social media message is displayed.

In some embodiments, the method further comprises launching anapplication installed on the mobile device, wherein the applicationcauses the first social media message to be displayed. In certainembodiments, the application causes the alert tone to be played on themobile device. In some embodiments, the application is installed on theSIM card of the mobile device. In other embodiments, the application isinstalled on the operating system of the mobile device. In still furtherembodiments, the method further comprises receiving, in the application,the first actionable response option selected by the user.

In other embodiments, the method further comprises: receiving, in theapplication, a communication comprising executable instructions tolaunch a browser of the mobile device and navigate the browser to awebsite; causing the browser of the mobile device to be launched; andcausing the browser to navigate to the website. In some embodiments, themethod further comprises: receiving, in the application, a second socialmedia message comprising a clickable link; and displaying the secondsocial media message on the screen of the mobile device.

DESCRIPTION OF THE FIGURES

FIG. 1 is a flowchart illustrating the basic architecture of theSocialLinX platform.

FIG. 2 is a flowchart illustrating the steps related to a phone callevent that will lead to the eventual triggering of the SocialLinXservice.

FIG. 3 is a flowchart illustrating the Mobile Operator Network as itwould interact with the SocialLinX server platform.

FIG. 4 is a flowchart illustrating the exemplary process of the logicthe SocialLinX platform uses to determine if a campaign message shouldbe sent to a specific targeted mobile subscriber.

FIG. 5 is a flowchart illustrating the exemplary process of how theSocialLinX application is expressed and interacts with the user device,and thus the user experience.

FIG. 6 is a flowchart illustrating the exemplary process of how theSocialLinX platform logs the mobile device user's response anddetermines if any follow-up questions should be sent as a result of theuser's response.

FIG. 7 is a flowchart illustrating the exemplary process of how theSocialLinX platform updates the database with subscriber preferenceresults, tracking the participation such that the MNO may modify thefrequency of campaign depending on subscriber responsiveness.

FIG. 8 is a flowchart illustrating the exemplary process of how aSocialLinX campaign is designed.

DETAILED DESCRIPTION

This application provides aspects and embodiments of OnePIN'sSocialLinX™ platform. The term “SocialLinX” is used throughout thisapplication to refer to multiple aspects and embodiments of the methods,applications, services, systems, and platforms disclosed herein. In someembodiments, SocialLinX is a cloud based platform that interacts with aclient application residing on the phone—either as a downloadableapplication from an external site, within the device OS or within a SIMcard. However, the name “SocialLinX” is not limited to any specificembodiment and can refer to multiple embodiments or individualembodiments. Furthermore, other names are also used to refer toembodiments described herein.

As used herein, the terms “a” and “an” mean one or more than one.

With SocialLinX, entities have the opportunity to increase theeffectiveness of their social networking communication channels withcustomers. Brands are able to target mobile subscribers who are usingsocial media channels, and can subsequently invite the mobile subscriberto connect on any social media platform. Notifications are all relevantand timely for subscribers as they only receive invitations for brandsthat interest them. As used herein, the term “entities” refers tobusinesses, companies, brands, corporations, partnerships, politicalcampaigns, education institutions, etc. These terms are usedinterchangeably to refer to entities that can use and benefit fromSocialLinX.

SocialLinX is preferably used with a mobile phone, but can also be usedwith other devices that can be configured to make phone calls or tonavigate the internet. For example, tablets and other computers thatinclude Skype or Google Voice can be utilized with the services.

SocialLinX Overview

SocialLinX focuses on enhancing the relationship a brand or enterpriseor any entity has with a consumer or follower. In one embodiment, amobile subscriber is able to indicate which social media platforms hecurrently utilizes, such as Facebook or Twitter. In one embodiment, thisis done via a remote application on the user's device which allows theuser to indicate which social media channels he uses, as well as toprovide credentials securely such that the SocialLinX application islinked to his social media accounts. In some embodiments, the user'ssocial media selections could also be entered via a web site front endto the SocialLinX platform. The SocialLinX cloud server stores thisinformation.

In some embodiments, when a subscriber makes a phone call to a brand,such as calling to book a flight on Lufthansa, the event triggerinformation is passed from the (MNO) Mobile Network Operator to theSocialLinX cloud. The cloud checks to determine if the subscriber isactive on any social networks and then sends a message to the subscriberinviting him to connect to the brand just called (i.e., Lufthansa) onsocial networking sites. Brands are able to enhance their relationshipwith interested consumers, who in turn are able to follow brands usingtheir own preferred social networking sites. Promotions, new product andservice launches, coupons, discounts, and new information can all beshared with the consumer on the social networking site—making it avaluable resource for the mobile subscriber and giving them a goodreason to connect to the brand.

Furthermore, subscribers are able to self-select brands that arerelevant to them, because they receive invitations only for brands theyhave called.

Additionally, brands can target groups of subscribers using specificsocial networks (tracked by the cloud platform), via a campaign-basedapproach. With this approach, in some embodiments, a set number ofsubscribers who are known social networking users are targeted at aspecific time. Subscribers do not need to opt-in to the service. In someembodiments, subscribers receive relevant notifications automatically asdetermined by the MNO. As used herein, the terms “user” and “subscriber”are used interchangeably.

In some embodiments, subscribers can opt-out from receivingnotifications anytime. When an invitation is sent to the subscriber, thesubscriber has the option to opt out, e.g., by selecting “stop allnotifications.” In addition, the subscriber can send a “STOP” SMSnotification to a designated shortcode which will automatically turn offthe service. In some embodiments, SocialLinX also has the intelligenceto ask the user if he would like to opt-out of the service if heconsistently chooses not to accept any of the invitations offered bythrough the service (e.g., by tracking the subscribers responses and,once a target number has been met, asking the subscriber if he wouldlike to opt out).

In one embodiment, the SocialLinX platform will offer the automaticopt-out opportunity if the user chooses not to accept consecutiveinvitation offers. In one embodiment, this automatic opt-outnotification could be sent to the user after a specific number ofconsecutive refusals. In other embodiments, the opt-out invitation canbe sent if the subscriber declines a percentage of invitation offers. Insome embodiments, the consecutive declines or percentage of declines aretracked over a specific time period before triggering the opt-outinvitation. These values are configurable and can be changed at anytime, as it is managed at the platform level. Subscriber selections aretracked within the cloud in order to manage the automatic opt-outprocess.

Market Trends and Subscriber Targets

Trends: Brands (e.g., corporations, companies, businesses, politicalgroups—any branded entity or group; these terms are used interchangeablythroughout this disclosure to refer to all of the entity typescollectively) must have a mobile advertising strategy in order tocontinue relationships with their consumer base. Mobility is key oftenkey to an advertising strategy. Companies are looking for creative waysto engage with their consumers via mobile devices and services, and togrow their base of followers on social media sites.

Service Availability: The service is relevant for any subscriber type(prepaid, postpaid, corporate subscribers, mass market, etc.).Application marketing can be targeted for specific segments.

Revenue: In one embodiment, brands are charged per campaign to promotetheir social media sites to targeted subscribers.

Service Benefits

Subscribers are able to connect to relevant brands at their discretion,and participate in promotions, special offers, and feedback surveys.

MNOs can offer a valuable advertising service to brands where a base ofknown social networking active users can be targeted.

Operation

The SocialLinX platform includes a web interface that enablesbusinesses, enterprises, marketers, etc. to log in and define acampaign. Within the campaign event, businesses or mobile operatorsenter all relevant information including but not limited to the targetphone number(s) that will trigger different services when called, andthe timeframe during which a campaign will be relevant.

The user interface specifics (i.e., the text mobile consumers will see)and the social media linkages can be entered via the web interface.

In one embodiment, the SocialLinX platform is connected to a mobilenetwork operator's call switch via an Application Programming Interface(API). In other embodiments, the cloud platform can also be connected tothe mobile operator's billing platform or HLR (Home Location Registry),or internet routing equipment via an API, depending on the operator'snetwork structure. When a designated campaign number is dialed (i.e., abusiness's phone number), the API informs the cloud platform. In someembodiments, the business phone number and the mobile subscriber'sMSISDN (Mobile Station International Subscriber Directory Number) areboth passed to the platform via the API. In some embodiments, the dateand time of the event are also passed to the platform.

When the platform receives communications via the API, the businessphone number is checked to determine which campaign should be executed(in some embodiments, there will be multiple campaigns for differentbusinesses running on the platform at the same time). The platform alsochecks the caller's phone number to determine if the calling party hasopted out from any services. If the calling party has opted out of theservice, then processing ends and no further communications are sent tothe mobile subscriber.

If the mobile user is not on the opt-out blacklist, then an appropriatecampaign message is prepared based on the configuration criteria andsent to the mobile subscriber. Here, this communication is described asa SMS which triggers a remote application on the mobile user's mobiledevice. This could be a binary SMS, standard text SMS, a specialized(flash, class 1) SMS, or a class 2 SMS which the handset passes to a SIMcard within the device. Alternatively, communications can occur via MMS,email, USSD, or via other web-based communications channels between themobile phone and the platform.

When the message is received on the calling party's mobile device, theclient application displays the prompt to the user. The user is able toselect a response, which is then sent back to the cloud via theapplication. Communication back to the cloud can be via a data channel,SMS, MMS, etc.

The above embodiments can also be implemented in a manner where a clientapplication (either on the phone or on the SIM card) is not required. Inthis instance, a USSD channel is opened and the communications betweenthe mobile subscriber and the platform occur via USSD communications.

In some embodiments, the cloud server can collect the device type of therespective mobile devices and can send a message to the respectiveclient applications to “turn off” the client application in mobiledevices that have known issues that interfere with the service.

In addition to after-call techniques, the service can be conducted in anintelligent campaign manner. In some embodiments, the server is able totrack calls that individual subscribers make to businesses. If abusiness would like to run a campaign at a later date, subscribers whohave called that business in the past can be targeted. This makes theprompts to the mobile subscribers relevant, as a previous relationshipwith the company had already been established by the mobile consumer.Consumers targeted in this manner receive a prompt, similar to thatoutlined in the before mentioned embodiments. The intelligent campaignscan be arranged to run a predefined dates and times, and for selectedgroups of subscribers in a regional area based on the subscriber's areacode.

Initially, the SocialLinX service triggers and displays prompts to theconsumer after a phone call or other user generated event, such asnavigating to a company website. First, a phone call is placed to abusiness currently running an SocialLinX campaign. After the phone callends, an interactive prompt is displayed on the screen of the mobiledevice. In some embodiments, a tone is played by the mobile device inconjunction with the displaying of the interactive prompt.

The text displayed to the calling party is fully configurable by thecompany or business that was called. In this example, a mobile usercalls an airline to make a reservation. After the phone call, the usersees an automatic, interactive prompt on her handset directly on thescreen.

In the embodiment where the mobile user interacts with the campaignmessage and chooses to accept the social media invitation, a message issent back to the SocialLinX platform. In some embodiments, a commandmessage is sent back to the remote application on the user's phone,which automatically launches the social media site for the specificbrand. In the embodiment where the user has provided correctcredentials, the SocialLinX platform can link the user directly to thebrand's social media account. For example, a user would begin to seenews and events in her Twitter feed from a specific brand, because theplatform was able to make the connection on her behalf.

FIG. 1 is a flowchart illustrating an exemplary embodiment of the basicarchitecture of the SocialLinX platform. In one embodiment, as picturedin FIG. 1, SocialLinX utilizes the following connectivity structure:

-   -   Mobile Subscriber A calls a number defined in the SocialLinX        target base (“1”). Alternatively, the user may navigate to a        website defined as a campaign target. The Operator Switch, HLR        (Home Location Registry), or web router bank are in        communication with the SocialLinX platform (“2”). This allows        for the Mobile Operator network to notify the SocialLinX        platform when a specific target phone number is dialed or when a        specific website is visited.    -   After a trigger event occurs and subsequently, the information        necessary to trigger a campaign is passed to the SocialLinX        platform (in some embodiments, via an API). Then, the platform        processes the information and prepares a campaign message to be        sent to a mobile subscriber.    -   In one embodiment, the SocialLinX platform is connected to a        Mobile Network Operator SMSC (Short Message Service Center) via        an SMPP (Short Message Peer-to-Peer) connection (“3”). Other        connection types in other embodiments are also possible. In some        embodiments, the platform may also be connected to an MNO's MMSC        (MultiMedia Message Service Center). The Operator SMSC forwards        the SocialLinX campaign message to Subscriber A's device (“4”).    -   The social media invitation appears on Subscriber A's device as        discussed above, at which point the subscriber selects his or        her preferred option. In one embodiment, if Subscriber A chooses        to accept the invitation, the SocialLinX application on the        device can launch the social media site for Subscriber A        automatically.    -   In some embodiments, the SocialLinX remote application within        Subscriber A's mobile device forwards the response to a        designated short code at the Operator SMSC (“5”) for logging and        further processing purposes.    -   The Operator SMSC receives and forwards the response to the        SocialLinX platform (“6”). In some embodiments, the response is        in the form of a binary SMS message.    -   In some embodiments, the platform parses the message and        determines an appropriate response to Subscriber A based on        Subscriber A's device type and interest in the campaign        promotion.    -   In the embodiment where Subscriber A chose to participate, the        platform can send a message back to the subscriber. This could        be a command message that the remote application processes and        further launches other applications on the device (such as a        Facebook application) or it may be an SMS (Short Message        Service) thanking the subscriber for participating. If the user        has a feature phone that does not support automatically        launching a web browser session from the SIM card or from the        remote application, the message sent back to Subscriber A may be        an SMS with links to social media sites. Subscriber A is then        able to click on the link, launch a social networking session,        and connect to the brand or company being promoted. These        messages would flow through the MNOs SMSC and MMSC respectively        (“7”).    -   The Operator SMSC forwards the contact information to the device        user “(8)”.

FIG. 2 is a flowchart illustrating the steps related to a trigger eventthat will lead to the eventual launching of the SocialLinX service. Instage 305, a trigger event occurs. In one embodiment, this could be acall a mobile user places to a business. In another embodiment, thistrigger event could be navigation to a website by a mobile user. Instage 310, the event begins, e.g., the call connects. A connected callcan have a multitude of scenarios including speaking with an actualindividual, interacting with an automated voice response system,connecting to a recorded message or voice mail system. In all cases, thecall will end as signified by stage 315 (“Event ends”). At this point,the call is disconnected and communications between the SocialLinXplatform (server) and the Mobile Operator's network continue, asoutlined in FIG. 3.

FIG. 3 is a flowchart illustrating the Mobile Operator Network as itwould interact with the SocialLinX server platform. In stage 405, anevent trigger ends. In one embodiment, this could be a Call Disconnect.The Call Disconnect is a formal event recognized by the Mobile Operatornetwork. This can be a caller initiated Call Disconnect, or a NetworkOriginated Call Disconnect Event, meaning the called party terminatesthe call or the network is not able to maintain the call and the calldrops.

In some embodiments, when the call ends, the Mobile Operator Networkwill automatically check the phone number dialed to determine if aSocialLinX campaign is associated with the number. In some embodiments,this information is stored within a database in the Mobile Operator'snetwork. In other embodiments, the information can be stored within theSocialLinX platform with regular communications between the MNO networkand the SocialLinX platform via web services or APIs. (ApplicationProgramming Interfaces). If the phone number dialed in this embodimentdoes not have a SocialLinX campaign defined, then the flow ends as shownin stage 415, and no further processing continues. If the phone numbercalled does have a campaign defined, then the MNO network informs theSocialLinX platform of the calling event as outlined in stage 420.Information needed to execute the social media promotional campaign onthe SocialLinX platform is passed from the MNO network to the platform.In some embodiments, this information includes the calling party'smobile MSISDN (Mobile Station International Subscriber DirectoryNumber). In this embodiment, the subscriber's mobile phone number isalso known as the OA, or Originating Address. In some embodiments, theMNO network may also provide time and date to the SocialLinX platform.In some embodiments, the called phone number, referred to as the DA orDestination Address, is also sent to the SocialLinX platform. Thisnumber may be a mobile phone number dialed, an international number, alandline or fixed number, a 1-800 phone number, a 1-900 phone number, anabbreviated number such as those used for emergency services such as911, a shortcode number often used in the mobile industry for ShortMessage Service (SMS) communications or any other number or addressmechanism used for connecting two or more parties to communicate. TheSocialLinX platform then continues processing, as outlined in FIG. 4.

FIG. 4 is a flowchart illustrating an exemplary embodiment of the logicprocess the SocialLinX platform uses to determine if a campaign messageshould be sent to a specific targeted mobile subscriber. In someembodiments, the SocialLinX platform receives the Origination Address,Destination Address, and other information including date and time fromthe MNO network as shown in stage 505. In stage 510, the SocialLinXplatform performs a check for the Destination Address to determine ifthe campaign is still relevant. In some embodiments, the SocialLinXplatform checks to see if the date and time settings fall withinpreconfigured allowable ranges. In some embodiments, the OriginatingAddress is also checked by the platform in stage 515. The platformchecks to determine if the user has opted out of receiving messagenotifications. In some embodiments, a mobile subscriber may opt out ofreceiving any SocialLinX notification for any brand, company, orbusiness, etc. called. In other embodiments, the platform and remoteapplication residing within the user's device are configured to allowthe user to manage which brands, businesses, companies, groups, etc.that he would like to received SocialLinX notifications from after phonecalls or other trigger events. At stage 515, the platform is alsochecking to ensure that the user has not exceeded pre-configurablecounters (e.g., whether the user has declined an invitation a specifiednumber of times or a specified percentage of times).

In one embodiment, the counters track the number of total SocialLinXmessages the user has received over a given timeframe for all brands andfor all trigger events. This tracking ensures that the user does notreceive an over abundance of social media messages in a short timeperiod, which could lead to him opting out of all notifications in thefuture. If the has exceeded the allowable limit, the processing ends asoutlined in stage 516. In some embodiments, this limit may be set by theuser. In other embodiments, the limit may be set by a networkadministrator within the MNO or may be set by an advertising agency orcompany managing the platform and overall user experience. In theembodiment where the user has not exceeded the predefined counterlimits, a SocialLinX message is prepared by the platform and sent to themobile subscriber at stage 520. The message sent could be a standardSMS, binary SMS, a class 2 SMS which will directly communication with aSIM (Subscriber Identity Module) card within the mobile subscriber'smobile device, an MMS message, a USSD message, or a web message sentover an IP (Internet Protocol) network. Processing on the user's devicethen ensues, as depicted in FIG. 5.

FIG. 5 is a flowchart illustrating an exemplary embodiment of how theSocialLinX application is expressed and interacts with the user device.This embodiment exemplifies the user experience. In stage 605, theSocialLinX remote application is triggered on the mobile user's device.In some embodiments, the application may play a configurable tone asshown in stage 610. In some embodiments, this tone can be configured bythe mobile user. In some embodiments, this tone can be configured by theplatform administrator. In some embodiments, the tone can also be turnedoff for specific subscribers, for specific campaigns, or for certaindevice types. After the tone is played, the campaign text is displayedto the mobile user as shown in stage 615. The text shown to a mobileuser is fully configurable and can contain letters, numbers, specialcharacters and punctuation, or may contain UCS2 Unicode encodedcharacters such as Greek, Cyrillic, or Mandarin characters as anexample. In most embodiments, the message displayed in stage 615 will beactionable by the calling party, meaning the user can make a decision asto whether or not he would like to accept the invitation being promotedvia the SocialLinX service. In stage 620, the user makes the decision.If he decides to ignore the prompt, or if he declines the invitation(e.g., by selecting “Cancel” or “No”), he sees no further informationand his “No” response is automatically sent back to the SocialLinXserver in stage 630. In one embodiment, the remote application is ableto automatically launch a browser session. In this instance, if the userdecides to accept the invitation at stage 620 (e.g., by selecting “OK”or “Yes”), the remote application will check if the user's device isable to launch a browser session, as outlined at stage 640. If themobile phone does not support an automatic launch of a browser, aresponse is sent back to the server at stage 645 indicating that thesubscriber accepted the invitation, and that the device does not supportan automatic browser launch. In some embodiments, the device type, asindicated by a mobile device TAC (Type Allocation Code) is also sentback to the SocialLinX platform. The platform continues processing, asoutlined in FIG. 6. In the embodiment where the mobile device cansupport the automatic launch of a browser and the campaign is definedsuch that a website should launch, the webpage is displayed on theuser's device at stage 650. At stage 655, a response is sent back to theserver indicating the user accepted the invitation and that the browserlaunch was successful. In some embodiments, the user's device type isalso sent to the platform.

FIG. 6 is a flowchart illustrating an exemplary embodiment of how theSocialLinX platform logs the mobile device user's response anddetermines the appropriate next steps based on the campaign definitionand the user's device type. At stage 705, the user's selected responseto the social media campaign is received at the SocialLinX platform. Instage 710, the server processes the response and determines if the userwas interested in the campaign. If the user was not interested, in someembodiments, the platform logs the response at stage 715. If the userwas interested, in some embodiments, the platform logs the response atstage 720, and then checks at stage 725 whether or not the devicesupported an automatic browser launch. If the device did not support thebrowser launch, then at stage 730 a follow-up message is prepared. Inone embodiment, this could be a standard SMS message. In one embodiment,the SMS can contain links to social media sites and platforms on whichthe company is inviting the subscriber to connect. An exemplary messagecould read:

-   -   “Thanks for being a great United Airlines customer. Like us on        Facebook and follow us on Twitter to receive the latest        promotions!”    -   www.facebook.com/unitedairlines    -   www.twitter.com/unitedairlines

The message is sent to the user at stage 735 and further logging withinthe platform, as exemplified by the flow in FIG. 7, continues. If thedevice did support a browser launch, the SocialLinX platform looks todetermine if any optional messages or follow-up should be sent to theuser and sends these messages at stage 740.

FIG. 8 is a flowchart illustrating the exemplary process of how theSocialLinX platform updates the database with subscriber preferenceresults, tracking the participation such that the MNO may modify thefrequency of campaign depending on subscriber responsiveness. At stage805, the SocialLinX server database is updated with the resulting userselection from a targeted mobile subscriber. The platform looks todetermine if the mobile user responded in a positive or negative fashionat stage 810 and updates configurable counters per MSISDN accordingly.

FIG. 8 is a flowchart illustrating an exemplary embodiment of how aSocialLinX campaign is designed. At stage 905, the campaign is definedwithin the server. In some embodiments, this includes the days and timesduring which the campaign will be relevant. Specific geographic regionscan also be configured. A maximum number of targeted mobile subscriberscan also be set. At stage 910, user or network generated events thatshould trigger a campaign are defined. In one embodiment, this mayinclude phone numbers called after which the campaign should trigger. Insome embodiments, this may include websites that should trigger acampaign when the mobile subscriber launches the web session, or ends aweb session for that specific address. Next, during stage 915, theactual campaign text that will be shown to a mobile subscriber isdefined. In one embodiment, a web site may launch immediately if theuser accepts the social media invitation. This specific website isdefined within the configuration at stage 920. In stage 925,configurable counters and rules for the campaign are set. In oneembodiment, this could include the number of times a specific uniquemobile subscriber, as defined by his MSISDN, is prompted to connect on asocial media platform.

EQUIVALENTS

It is to be understood that the foregoing description is intended toillustrate and not limit the scope of the invention, which is defined bythe scope of the appended claims. Those skilled in the art willrecognize, or be able to ascertain, using no more than routineexperimentation, numerous equivalents to the specific embodimentsdescribed specifically in this disclosure. Such equivalents, and otheraspects, advantages, and modifications are within the scope of thefollowing claims.

1. A computer-implemented method for automatically prompting a user tofollow an entity on a social media network on a mobile device after atriggering event, the method comprising: receiving, at a server, anindication that a triggering event has occurred; receiving, at theserver, an indication that the triggering event matches a triggeringevent stored in a database operably connected to the server; receiving,at the server, a communication comprising the Mobile StationInternational Subscriber Directory Number of the mobile device;preparing a first social media message comprising one or more firstactionable response options; and sending the first social media messageto the mobile device.
 2. The method of claim 1, further comprising:receiving, at the server, a communication comprising the firstactionable response option selected on the mobile device; preparing asecond social media message comprising executable instructions to launcha browser on the mobile device and to navigate the browser to a socialmedia website address; and sending the second social media message tothe mobile device.
 3. The method of claim 2, further comprising loggingthe first actionable response option selected by the user.
 4. The methodof claim 3, further comprising determining whether social media messagessent to the mobile device have exceeded a preset amount.
 5. The methodof claim 2, wherein the communication further comprises the device typeof the mobile device and information regarding whether the mobile devicesupports browser launch from executable instructions contained within areceived message.
 6. The method of claim 5, further comprising:preparing an SMS message comprising a browser launch link; and sendingthe SMS message to the mobile device, wherein the SMS message isprepared and sent when the information indicates that the mobile devicedoes not support browser launch from instructions contained within areceived message.
 7. The method of claim 1, wherein the triggering eventis selected from the group consisting of a phone call placed from themobile device to a first phone number, a phone call received at themobile device from a second phone number, navigation to a specific webaddress on the mobile device, and navigation away from a specific webaddress on the mobile device.
 8. The method of claim 7, wherein thetriggering event is a phone call placed from the mobile device to afirst phone number.
 9. The method of claim 1, wherein the entity isselected from the group consisting of a business, a university, and apolitical campaign.
 10. The method of claim 1, wherein the social medianetwork is selected from the group consisting of Facebook, Instagram,Twitter, Google+, LinkedIn, Renren, Snapchat, Tumblr, Pinterest, andYouTube.
 11. The method of claim 1, wherein the first social mediamessage is selected from the group consisting of binary SMS, flash SMS,MMS, standard SMS, USSD notification, and email.
 12. Acomputer-implemented method for automatically prompting a user to followan entity on a social media network after a triggering event on a mobiledevice, the method comprising: receiving, at the processor in the mobilephone, an indication that a triggering event has occurred; receiving atthe mobile device a first social media message comprising one or morefirst actionable response options; and displaying on the screen of themobile device the first social media message.
 13. The method of claim12, further comprising playing an alert tone on the mobile device whenthe first social media message is displayed.
 14. The method of claim 12,further comprising launching an application installed on the mobiledevice, wherein the application causes the first social media message tobe displayed.
 15. The method of claim 14, wherein the application causesthe alert tone to be played on the mobile device.
 16. The method ofclaim 14, wherein the application is installed on the SIM card of themobile device.
 17. The method of claim 14, wherein the application isinstalled on the operating system of the mobile device.
 18. The methodof claim 14, further comprising receiving, in the application, the firstactionable response option selected by the user.
 19. The method of claim18, further comprising: receiving, in the application, a communicationcomprising executable instructions to launch a browser of the mobiledevice and navigate the browser to a website; causing the browser of themobile device to be launched; and causing the browser to navigate to thewebsite.
 20. The method of claim 18, further comprising: receiving, inthe application, a second social media message comprising a clickablelink; and displaying the second social media message on the screen ofthe mobile device. 21.-25. (canceled)